home *** CD-ROM | disk | FTP | other *** search
- Path: newton.whit.org!krw
- From: krw@PROBLEM_WITH_INEWS_DOMAIN_FILE (krw)
- Newsgroups: comp.unix.programmer,comp.lang.c
- Subject: Re: Runtime ANSI C checking tool?
- Followup-To: comp.unix.programmer,comp.lang.c
- Date: 11 Mar 1996 08:29:36 GMT
- Organization: CSAC
- Message-ID: <4i0o9g$t79@natasha.rmii.com>
- References: <DnI89B.EnH@pgh.nauticom.net> <p5ag239ede.fsf@lemming.wellfleet.com> <TANMOY.96Mar7180501@qcd.lanl.gov> <826474756snz@genesis.demon.co.uk>
- NNTP-Posting-Host: newton.whit.org
- X-Newsreader: TIN [version 1.2 PL2]
-
- Lawrence Kirby (fred@genesis.demon.co.uk) wrote:
- : In article <TANMOY.96Mar7180501@qcd.lanl.gov>
- : tanmoy@qcd.lanl.gov "Tanmoy Bhattacharya" writes:
-
- : >In article <826219697snz@genesis.demon.co.uk>
- : >Lawrence Kirby <fred@genesis.demon.co.uk> writes:
- : >
- : >LK: >Well, a well-written ANSI C compiler should handle all language
- : >LK: >violations, and a well-written ANSI C system library should catch all
- : >LK: >runtime violations (passing NULL to strcpy() or something, for
- : >LK: >example).
- : >LK:
-
- I don't know about the NULL stuff, but the man page on my gcc compiler
- gives -ansi -pedantic for the switches to cause the compiler to reject
- non-standard C source code. I don't know if it works, but try using
- curses or something and see if it works
-
- Ken.
-
- --
- /--\--/--\--/--\--/--\--/--\--/--\--/--\--/--\--/--\--/--\--/--\--/--\--/--\
- \ The Whittaker's domain! /
- / Try our MUD (Multi User Domain) \
- \ Come to: /
- / aGe oF iNsaNitY \
- \ telnet to: newton.whit.org 4000 /
- /--\--/--\--/--\--/--\--/--\--/--\--/--\--/--\--/--\--/--\--/--\--/--\--/--\
-